integrate lightspeed MCP into selected skills to increase 'Red Hat' footprint and utilize the tools it provides#14
Merged
Conversation
…ootprint and utilize the tools it provides
Contributor
There was a problem hiding this comment.
Pull request overview
This PR adds an optional Red Hat Insights / Lightspeed MCP integration to the RHEL deployment and debugging skills, and wires up a new MCP server entry so those skills can query inventory/CVEs/lifecycle/advisor data when credentials are available.
Changes:
- Add optional Red Hat Insights checks to
/rhel-deploy(pre-deploy) and/debug-rhel(diagnostic augmentation). - Register a new
lightspeed-mcpMCP server in.mcp.jsonand document it in the repo README. - Extend
/debug-rheloutputs and summary tables to include Insights/CVE-related info.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| rh-developer/skills/rhel-deploy/SKILL.md | Adds an optional Phase 2b Insights pre-deploy check and documents the optional server. |
| rh-developer/skills/debug-rhel/SKILL.md | Adds an optional Insights phase (CVEs + advisor rules), updates summary/output documentation, and lists optional MCP tools. |
| rh-developer/README.md | Documents optional Insights prerequisites and adds a Lightspeed/Insights MCP server entry. |
| rh-developer/.mcp.json | Adds a lightspeed-mcp server definition using env-only credentials. |
Comments suppressed due to low confidence (5)
rh-developer/README.md:45
- README lists the MCP server as lightspeed, but the configured server key in
.mcp.jsonand the skills refer tolightspeed-mcp. This inconsistency will confuse users (and theToolSearchprefix) when enabling the server; align the name across README and config (either rename the server key or update the README entry).
- **openshift** - OpenShift cluster management and Helm deployments
- **podman** - Container image management and local builds
- **github** - Repository browsing and code analysis
- **lightspeed** - Red Hat Insights data (vulnerability, advisor, inventory, planning) — optional
rh-developer/README.md:38
- The new prerequisite mentions an Insights service account, but it doesn’t tell users which environment variables to set. Since
.mcp.jsonexpectsLIGHTSPEED_CLIENT_IDandLIGHTSPEED_CLIENT_SECRET, consider documenting those names here (or linking to a setup doc) so users can actually enable the optional server.
- GitHub personal access token (for GitHub integration)
- Red Hat Insights service account with Client ID and Secret (optional, for vulnerability and advisor data in `/debug-rhel` and `/rhel-deploy`)
rh-developer/skills/debug-rhel/SKILL.md:332
- After this change, the prompt "Continue to diagnosis summary?" appears immediately before the new optional Insights phase, so it no longer matches what will happen next. Adjust the Phase 6 checkpoint wording (e.g., continue to optional Insights check / next phase) or move/remove it to avoid double confirmations and misleading flow.
Continue to diagnosis summary? (yes/no)
WAIT for user confirmation before proceeding.
Phase 7: Red Hat Insights Check (Optional)
This phase runs only if the lightspeed-mcp server is available. Use ToolSearch to check for Lightspeed MCP tools. If not available, skip this phase silently and proceed to Phase 8.
**rh-developer/skills/debug-rhel/SKILL.md:335**
* `RHEL_HOST` is defined as `user@host` in this skill, but Phase 7 instructs using "the hostname from `RHEL_HOST`" directly with `find_host_by_name`. Update the instructions to explicitly extract just the host portion (and not the `user@` prefix / optional port) before querying Insights inventory.
Step 1: Use find_host_by_name with the hostname from RHEL_HOST to look up the system in Red Hat Insights.
**rh-developer/skills/debug-rhel/SKILL.md:516**
* `INSIGHTS_SYSTEM_ID` and `CVE_COUNT` are listed as output variables, but Phase 7 doesn’t instruct storing them in session state when the Insights lookups succeed. Either add explicit "Store …" steps in Phase 7 or remove these from the output table to keep the skill spec internally consistent.
| INSIGHTS_SYSTEM_ID | Insights system ID (if registered) | abc-def-123 |
| CVE_COUNT | Number of CVEs affecting system | 3 |
</details>
---
💡 <a href="/RHEcosystemAppEng/agentic-collections/new/main?filename=.github/instructions/*.instructions.md" class="Link--inTextBlock" target="_blank" rel="noopener noreferrer">Add Copilot custom instructions</a> for smarter, more guided reviews. <a href="https://docs.github.com/en/copilot/customizing-copilot/adding-repository-custom-instructions-for-github-copilot" class="Link--inTextBlock" target="_blank" rel="noopener noreferrer">Learn how to get started</a>.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.